-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
start
: Avoid string concatenation in inline asm.
#21056
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please use string literals only for inline assembly in preparation for #10761.
abb0bb4
to
638be20
Compare
Done, and also included a workaround in the LLVM backend to ensure that frame pointers don't get used in naked functions. |
start
: Fix ++
usage in inline asm string construction.start
: Avoid string concatenation in inline asm.
638be20
to
c37f00e
Compare
Folded #21070 into this one and removed the |
For csky, we can just always do the gb initialization. For riscv, the gp code is temporarily pulled above the main switch until the blocking issue is resolved.
c37f00e
to
7a8e86e
Compare
Thank you, looks great. |
I had the operator precedence wrong.
For csky, there are currently some LLVM issues blocking full compilation, so that mistake slipped through rather unsurprisingly. For riscv, I first added the
gp
initialization code unconditionally and tested it, but then I added the condition to exclude that code in self-hosted and neglected to actually test it with LLVM afterwards. The result was that it worked fine with the self-hosted backend, but not so with LLVM (which we have no CI coverage for due to #18872).